fix(near): correct token attribution in tx parsing, harden intents actuals - #12525

Description

A NEAR Intents swap (NEAR → USDT on NEAR) displayed an absurd completed amount ("5,651,948,527,226,708,191.126278 USDT" for a ~1 USDT swap). Investigation traced every source feeding the displayed actual amount; two real defects were found and fixed on those paths:

• parseTx token mis-attribution: every NEP-141 event in a transaction was labeled with the transaction's top-level receiver as the token contract. For intents settlements (receiver intents.near), the USDT ft_transfer to the user was attributed to nep141:intents.near, so useActualBuyAmountCryptoPrecision's chain-side lookup could never match the buy asset and the fallback chain silently failed. Events are now attributed per-receipt to the executor — the contract that actually emitted the event — which is correct for any transaction shape (delegated, batched, multi-contract).
• Intents checkTradeStatus over-trusted swapDetails.amountOut: it was reported as actualBuyAmountCryptoBaseUnit in every status. It is only reliably destination-denominated on terminal SUCCESS; in-flight and refund states no longer supply it, so a transient settlement-phase value can never be persisted as the actual amount (once written, it was never re-read from a corrected poll if polling stopped).

Verified live against the affected swap's settlement transaction (DJaLoG… / deposit c0f7e4…): the parse now returns exactly Receive 996459 under near:mainnet/nep141:usdt.tether-token.near — matching the provider's own swapDetails.amountOut and explorer (0.996459 USDT). Also verified the full quote path is decimals-clean end to end: provider registry (6 decimals), our asset (precision 6), request amount (wNEAR 24dp), quote amountOut (6dp).

Issue (if applicable)

closes #

Risk

Low. NEAR-only parsing plus one status-field gate. The executor attribution strictly improves correctness for all NEP-141 event shapes; plain ft_transfer transactions (receiver = token contract = executor) are unchanged.

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

NEAR transaction parsing for display/actual-amount purposes and NEAR Intents swap status reporting. No transaction construction changes.

Testing

Engineering

• Live parseTx against the affected settlement tx before/after: mislabeled nep141:intents.near → correct nep141:usdt.tether-token.near, value exact (996459).
• Full event dump of all three NEAR transactions of the swap via archival RPC confirms the corrupted figure exists nowhere on-chain — it could only be app-side, on the paths fixed here.
• 1-click status and SDK responses verified to carry the correct 6-decimal amountOut on SUCCESS.
• tsc clean on chain-adapters and swapper.

Operations

• Do a NEAR Intents swap into a NEAR-chain token: the completion notification and action center should show the actual received amount at sane magnitude.

Screenshots (if applicable)

🤖 Generated with Claude Code